Wireless communication method and terminal device

ABSTRACT

Implementations of the present disclosure provide a wireless communication method and a terminal device. In the case that a duplicate transmission of a first bearer is deactivated, a terminal device can determine an RLC entity of the split transmission. The wireless communication method includes: in the case that a duplicate transmission of a first bearer is deactivated, a terminal device determines, according to cell groups corresponding to a primary RLC entity and a secondary RLC entity in at least three RLC entities configured for the first bearer, an RLC entity that transmits a PDCP PDU, and/or a terminal device determines, according to cell groups corresponding to a primary RLC entity and a secondary RLC entity in at least three RLC entities configured for the first bearer, an MAC entity that maps the data amount of a PDCP to be transmitted.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S.application Ser. No. 17/469,619 filed on Sep. 8, 2021, which is acontinuation application of International PCT Application No.PCT/CN2019/127665, filed on Dec. 23, 2019. The entire contents of theabove-identified applications are hereby incorporated by reference.

TECHNICAL FIELD

Implementations of the present disclosure relate to the field ofcommunications, and more particularly, to a wireless communicationmethod and a terminal device.

BACKGROUND

In a New Radio (NR) system, in order to improve reliability of datatransmission, a terminal device may adopt a mode of duplicationtransmission. Specifically, in Release 15 (Rel-15), one bearer may beconfigured with two Radio Link Control (RLC) entities. A Packet DataConvergence Protocol (PDCP) layer corresponding to the bearer may copy aPDCP Protocol Data Unit (PDU) into two identical copies, for example oneis a PDCP PDU and another is a Duplicated PDCP PDU. The two PDCP PDUspass through different RLC layers and Media Access Control (MAC) layers,and finally are transmitted to a network device through an airinterface. In addition, when duplication transmission is deactivated anda condition for split transmission is met, the terminal device maytransmit split data through two RLC entities corresponding to thebearer, that is, different data are transmitted through different RLCentities.

In Release 16 (Rel-16, R16), it is considered to configure more RLCentities for a bearer, such as four RLC entities. In this case, how todetermine an RLC entity for split transmission is an urgent problem tobe solved.

SUMMARY

Implementations of the present disclosure provide a wirelesscommunication method and a terminal device, and the terminal device maydetermine an RLC entity for split transmission in a case thatduplication transmission of a first bearer is deactivated.

In a first aspect, there is provided a wireless communication method,wherein the method includes: in a case that duplication transmission ofa first bearer is deactivated, a terminal device determines an RLCentity for transmitting a PDCP PDU according to cell groupscorresponding to a primary RLC entity and a secondary RLC entity amongat least three RLC entities configured for the first bearer, and/ordetermines an MAC entity to which PDCP data volume pending fortransmission is mapped according to cell groups corresponding to aprimary RLC entity and a secondary RLC entity among at least three RLCentities configured for the first bearer.

In a second aspect, there is provided a wireless communication method,wherein the method includes: in a case that duplication transmission ofa first bearer is deactivated, a terminal device determines cell groupscorresponding to a primary RLC entity and a secondary RLC entity amongat least three RLC entities configured for the first bearer according toindication information for the first bearer; the terminal devicedetermines an RLC entity for transmitting a PDCP PDU according to thecell groups corresponding to the primary RLC entity and the secondaryRLC entity among the at least three RLC entities, and/or the terminaldevice determines an MAC entity to which PDCP data volume pending fortransmission is mapped according to the cell groups corresponding to theprimary RLC entity and the secondary RLC entity among the at least threeRLC entities.

In a third aspect, there is provided a wireless communication method,wherein the method includes: in a case that duplication transmission ofa first bearer is deactivated and there is no secondary RLC entity or nosecondary RLC entity is configured among at least three RLC entitiesconfigured for the first bearer, a terminal device determines whether tocarry out split transmission, or determines an RLC entity fortransmitting a PDCP PDU.

In a fourth aspect, there is provided a terminal device configured toperform the method in the first aspect or various implementationsthereof.

Specifically, the terminal device includes function modules configuredto perform the method of the first aspect described above or any ofvarious implementations thereof.

In a fifth aspect, there is provided a terminal device configured toperform the method in the second aspect or various implementationsthereof.

Specifically, the terminal device includes function modules configuredto perform the method in the above second aspect or variousimplementations thereof.

In a sixth aspect, there is provided a terminal device configured toperform the method in the third aspect or various implementationsthereof.

Specifically, the terminal device includes function modules configuredto perform the method in the third aspect or various implementationsthereof.

In a seventh aspect, a terminal device is provided, including aprocessor and a memory. The memory is configured to store a computerprogram, and the processor is configured to call and run the computerprogram stored in the memory to perform the method in the above firstaspect or various implementations thereof.

In an eighth aspect, a terminal device is provided, including aprocessor and a memory. The memory is configured to store a computerprogram, and the processor is configured to call and run the computerprogram stored in the memory to perform the method of the second aspector various implementations thereof.

In a ninth aspect, there is provided a terminal device, including aprocessor and a memory. The memory is configured to store a computerprogram, and the processor is configured to call and run the computerprogram stored in the memory to perform the method of the third aspectdescribed above or various implementation modes of the third aspect.

In a tenth aspect, there is provided an apparatus configured toimplement the method in any one of the first to third aspects or variousimplementations thereof.

Specifically, the apparatus includes a processor configured to call andrun a computer program from a memory to enable a device in which theapparatus is installed to perform the method in any one of the first tothird aspects or various implementation modes thereof.

In an eleventh aspect, there is provided a computer readable storagemedium configured to store a computer program that enables a computer toperform the method in any one of the first to third aspects or variousimplementations thereof.

In a twelfth aspect, there is provided a computer program productincluding computer program instructions that enable a computer toperform the method in any one of the first to third aspects or variousimplementations thereof.

In a thirteenth aspect, there is provided a computer program, which,when being run on a computer, enables the computer to perform the methodin any one of the first to third aspects or various implementationsthereof.

According to a technical solution of the first aspect, in a case thatduplication transmission of a first bearer is deactivated, a terminaldevice may determine an RLC entity for transmitting a PDCP PDU accordingto cell groups corresponding to a primary RLC entity and a secondary RLCentity among at least three RLC entities configured for the firstbearer, and/or determine an MAC entity to which PDCP data volume pendingfor transmission is mapped.

According to a technical solution of the second aspect, in a case thatduplication transmission of a first bearer is deactivated, a terminaldevice may determine cell groups corresponding to a primary RLC entityand a secondary RLC entity among at least three RLC entities configuredfor the first bearer based on indication information for the firstbearer sent by a network device, and further determine an RLC entity fortransmitting a PDCP PDU, and/or, determine an MAC entity to which PDCPdata volume pending for transmission is mapped.

According to a technical solution of the third aspect, in a case thatduplication transmission of a first bearer is deactivated and there is asecondary RLC entity among at least three RLC entities configured forthe first bearer, a terminal device determines an RLC entity fortransmitting a PDCP PDU.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of an architecture of a communicationsystem provided according to an implementation of the presentdisclosure.

FIG. 2 is a schematic diagram of an architecture of a duplicationtransmission mode.

FIG. 3 is a schematic flow chart of a wireless communication methodprovided according to an implementation of the present disclosure.

FIG. 4 is a schematic diagram of a primary RLC entity and a secondaryRLC entity provided according to an implementation of the presentdisclosure.

FIG. 5 is a schematic diagram of another primary RLC entity and anothersecondary RLC entity provided according to an implementation of thepresent disclosure.

FIG. 6 is a schematic diagram of another primary RLC entity and anothersecondary RLC entity provided according to an implementation of thepresent disclosure.

FIG. 7 is a schematic diagram of yet another primary RLC entity andanother secondary RLC entity provided according to an implementation ofthe present disclosure.

FIG. 8 is a schematic flow chart of determining a PDCP PDU transmissionmode provided according to an implementation of the present disclosure.

FIG. 9 is another schematic flow chart of determining a PDCP PDUtransmission mode provided according to an implementation of the presentdisclosure.

FIG. 10 is a schematic flow chart of determining a mode for mapping PDCPdata volume provided according to an implementation of the presentdisclosure.

FIG. 11 is another schematic flow chart of determining a mode formapping PDCP data volume provided according to an implementation of thepresent disclosure.

FIG. 12 is a schematic flow chart of another wireless communicationmethod provided according to an implementation of the presentdisclosure.

FIG. 13 is a schematic flowchart of yet another wireless communicationmethod provided according to an implementation of the presentdisclosure.

FIG. 14 is a schematic block diagram of a terminal device providedaccording to an implementation of the present disclosure.

FIG. 15 is a schematic block diagram of another terminal device providedaccording to an implementation of the present disclosure.

FIG. 16 is a schematic block diagram of yet another terminal deviceprovided according to an implementation of the present disclosure.

FIG. 17 is a schematic block diagram of a communication device providedaccording to an implementation of the present disclosure.

FIG. 18 is a schematic block diagram of an apparatus provided accordingto an implementation of the present disclosure.

FIG. 19 is a schematic block diagram of a communication system providedaccording to an implementation of the present disclosure.

DETAILED DESCRIPTION

Technical solutions in implementations of the present disclosure will bedescribed below with reference to the drawings in the implementations ofthe present disclosure. It is apparent that the implementationsdescribed are just some of the implementations of the presentdisclosure, but not all of the implementations of the presentdisclosure. According to the implementations of the present disclosure,all other implementations achieved by a person of ordinary skill in theart without paying an inventive effort are within the protection scopeof the present disclosure.

The implementations of the present disclosure may be applied to variouscommunication systems, such as a Global System of Mobile Communication(GSM) system, a Code Division Multiple Access (CDMA) system, a WidebandCode Division Multiple Access (WCDMA) system, a General Packet RadioService (GPRS), a Long Term Evolution (LTE) system, an Advanced LongTerm Evolution (LTE-A) system, a New Radio (NR) system, an evolutionsystem of an NR system, an LTE-based access to unlicensed spectrum(LTE-U) system, an NR-based access to unlicensed spectrum (NR-U) system,a Universal Mobile Telecommunications System (UMTS), Wireless Local AreaNetworks (WLAN), Wireless Fidelity (WiFi), a next generationcommunication system or other communication systems.

Generally speaking, traditional communication systems support a limitedquantity of connections and are easy to implement. However, with thedevelopment of communication technology, mobile communication systemswill not only support traditional communication, but also support, forexample, device to device (D2D) communication, machine to machine (M2M)communication, machine type communication (MTC), vehicle to vehicle(V2V) communication, and the implementations of the present disclosuremay also be applied to these communication systems.

Optionally, a communication system in the implementations of the presentdisclosure may be applied to a carrier aggregation (CA) scenario, a dualconnectivity (DC) scenario, or a standalone (SA) networking scenario.

Implementations of the present disclosure do not limit frequencyspectrums applied. For example, implementations of the presentdisclosure may be applied to both licensed spectrum and unlicensedspectrum.

Illustratively, a communication system 100 applied in an implementationof the present disclosure is shown in FIG. 1 . The communication system100 may include a network device 110. The network device 110 may be adevice that communicates with terminal devices 120 (or referred to ascommunication terminals, or terminals). The network device 110 mayprovide communication coverage for a specific geographical area, and maycommunicate with terminal devices located within the coverage area.

FIG. 1 illustrates one network device and two terminal devices.Optionally, the communication system 100 may include multiple networkdevices, and other numbers of terminal devices may be included withinthe coverage range of each network device, which are not limited in theimplementations of the present disclosure.

Optionally, the communication system 100 may include other networkentities, such as a network controller and a mobile management entity,which is not limited in the implementations of the present disclosure.

It should be understood that a device with a communication function in anetwork/system in the implementations of the present disclosure may bereferred to as a communication device. Taking the communication system100 shown in FIG. 1 as an example, communication devices may include anetwork device 110 and terminal devices 120 which have communicationfunctions, and the network device 110 and the terminal devices 120 maybe the specific devices described above, and will not be describedrepeatedly herein. The communication devices may also include otherdevices in the communication system 100, such as network controllers andmobile management entities and other network entities, which are notlimited in the implementations of the present disclosure.

It should be understood that the terms “system” and “network” are oftenused interchangeably herein. The term “and/or” herein describes anassociation relation between associated objects only, indicating thatthere may be three relations, for example, A and/or B may indicate threecases: A alone, both A and B, and B alone. In addition, the symbol “/”herein generally indicates that there is a “or” relationship between theassociated objects before and after “/”.

Implementations of the present disclosure describe variousimplementations in combination with a terminal device and a networkdevice, wherein the terminal device may also be referred to a UserEquipment (UE), an access terminal, a subscriber unit, a subscriberstation, a mobile station, a mobile platform, a remote station, a remoteterminal, a mobile device, a user terminal, a terminal, a wirelesscommunication device, a user agent, or a user apparatus, etc. Theterminal device may be a STATION (ST) in WLAN, a cellular phone, acordless phone, a Session Initiation Protocol (SIP) phone, a WirelessLocal Loop (WLL) station, a Personal Digital Assistant (PDA) device, ahandheld device with a wireless communication function, a computingdevice or other processing device connected to a wireless modem, avehicle-mounted device, a wearable device, and a next generationcommunication system, such as, a terminal device in an NR network, or aterminal device in a future evolving Public Land Mobile Network (PLMN),etc.

By way of example but not limitation, in an implementation of thepresent disclosure, the terminal device may also be a wearable device. Awearable device may also be referred to a wearable intelligent device,which is a general term of wearable devices developed by intelligentdesign of daily wear using wearing technology, e.g., glasses, gloves,watches, clothing, shoes, etc. A wearable device is a portable devicethat is worn directly on a body or integrated into the clothes oraccessories of a user. Wearable devices are not only hardware devices,but also realize powerful functions through software support, datainteraction and cloud interaction. Generalized wearable smart devicesinclude devices that are full functioned, large sized, and may realizecomplete or partial functions without relying on smart phones, such assmart watches or smart glasses, etc., and include devices that onlyfocus on a certain kind of application and need to be used inconjunction with other devices such as smart phones, such as varioussmart bracelets and smart jewelry for monitoring physical signs.

The network device may be a network device for communicating with amobile device, or may be an Access Point (AP) in a WLAN, or a BaseTransceiver Station (BTS) in GSM or CDMA, or may be a NodeB (NB) inWCDMA, or an Evolutional Node B (eNB or eNodeB) in LTE, or a relaystation or an access point, or a vehicle-mounted device, a wearabledevice, a network device or a base station (gNB) in an NR network, or anetwork device in a future evolved PLMN network.

In the implementations of the present disclosure, a network device mayprovide a service for a cell, and a terminal device communicates withthe network device through a transmission resource (e.g., a frequencydomain resource or a spectrum resource) used by the cell, which may be acell corresponding to the network device (e.g., a base station). A cellmay belong to a macro base station, or a base station corresponding to aSmall cell. The Small cell here may include: a Metro cell, a Micro cell,a Pico cell, a Femto cell, etc. These Small cells have characteristicsof small coverage range and low transmission power, and are suitable forproviding high-speed data transmission services.

With reference to FIG. 2 , duplication transmission method in a DualConnection (DC) or Carrier Aggregation (CA) scenario in animplementation of the present disclosure is briefly introduced.

In a Dual Connection (DC) scenario, multiple network nodes (cell group(CG)) may serve a terminal device, and duplication transmission may becarried out between the cell groups and the terminal device. It shouldbe understood that in the implementations of the present disclosure, aCG may be equivalent to a network node, or a network device, etc.

Specifically, in a DC scenario, a protocol architecture of a duplicationtransmission mode may be shown in DRB 2 in FIG. 2 . A Packet DataConvergence Protocol (PDCP) is located in a CG (for example, a Master CG(MCG) or a Secondary CG (SCG), which may also be called a Master Node(MN) or a Secondary Node (SN)). The PDCP duplicates a PDCP PDU into twosame copies, for example, one is a PDCP PDU and the other is aduplicated PDCP PDU. The two PDCP PDUs pass through Radio Link Control(RLC) layers and Media Access Control (MAC) layers of different CGs, andreach a corresponding MAC layer and RLC layer of a terminal device(downlink) or a base station (uplink) through an air interfacerespectively, and finally are converged at a PDCP layer. When the PDCPlayer detects that the two PDCP PDUs are the same duplicated version,one of the two PDCP PDUs may be discarded, and the other PDCP PDU may besubmitted to a higher layer.

In the implementations of the present disclosure, two PDCP PDUs aretransmitted through different CGs, a purpose of frequency diversity gainmay be achieved, and thus reliability of data transmission can beimproved.

It should be understood that for a bearer configured with duplicationtransmission (for example, a Data Radio Bearer (DRB) or a SignalingRadio Bearer (SRB)), duplication transmission function of a bearer maybe dynamically activated or deactivated through a MAC Control Element(CE).

In addition, in an implementation of the present disclosure, an entityused for transmitting replicated data in a lower layer of a PDCP may becalled a leg or path, or may be replaced by a Logical Channel (LCH),that is, an RLC entity may be replaced by a leg or a Logical Channel.Accordingly, an RLC entity identifier may be replaced by an LCHidentifier or a leg identifier.

In a CA scenario, a protocol architecture of a duplication transmissionmode may be as shown in DRB 1 or DRB 3 in FIG. 2 . The duplicationtransmission mode adopts a protocol architecture of CA. Specifically,when duplication transmission is activated, data (PDU and replicateddata of PDU) generated by a PDCP layer are transmitted to two differentRLC entities, which are mapped to different physical layer carriersthrough the same MAC layer entity. It should be understood that in theimplementations of the present disclosure, data (PDU and replicated dataof PDU) generated by a PDCP layer is mapped to different physical layercarriers through two different RLC entities respectively, thus a purposeof frequency diversity gain can be achieved, and further reliability ofdata transmission can be improved.

In a case that duplication transmission is deactivated and a conditionfor split transmission is met, a terminal device may also use two RLCentities corresponding to the bearer to transmit split data, that is,transmit different data through the two RLC entities. The condition forsplit transmission may be that PDCP data volume and RLC data volume ofthe two RLC entities pending for transmission are greater than or equalto a preset threshold.

The above is a duplication transmission mode in which only two RLCentities are supported. In R16, it is a duplication transmission mode inwhich at least two RLC entities are supported. Specifically, in a casethat duplication transmission is activated, an architecture of CA, anarchitecture of DC, or an architecture combining DC and CA may beadopted for duplication transmission. Similarly, data (PDU and duplicatedata of PDU) generated by a PDCP layer are mapped to a lower layerthrough at least two different RLC entities for transmission, so as toachieve a purpose of frequency diversity gain and further improvereliability of data transmission.

However, in a case that duplication transmission is deactivated, it mayfall back to split transmission. When falling back to splittransmission, a secondary leg for split transmission may be indicated byRadio Resource Control (RRC). However, at this time, whether a primaryleg and a secondary leg may belong to the same CG, and how to performtransmission if the primary leg and the secondary leg belong to the sameCG, is an urgent problem to be solved.

The following describes in detail a split transmission solution designedfor the above technical problems in the present disclosure.

FIG. 3 is a schematic flow chart of a wireless communication method 200provided according to an implementation of the present disclosure. Themethod 200 may be performed by a terminal device in a communicationsystem shown in FIG. 1 . As shown in FIG. 3 , the method 200 may includeat least part of the following content.

In S210, in a case that duplication transmission of a first bearer isdeactivated, a terminal device determines an RLC entity for transmittinga PDCP PDU according to cell groups corresponding to a primary RLCentity and a secondary RLC entity among at least three RLC entitiesconfigured for the first bearer, and/or the terminal device determinesor indicates PDCP data volume pending for transmission.

Optionally, in S210, in a case that the duplication transmission of thefirst bearer is deactivated, the terminal device determines or indicatesPDCP data volume pending for transmission according to the cell groupscorresponding to the primary RLC entity and the secondary RLC entityamong the at least three RLC entities configured for the first bearer.

Further, in S210, in a case that the duplication transmission of thefirst bearer is deactivated, the terminal device determines or indicatesan MAC entity to which the PDCP data volume pending for transmission ismapped according to the cell groups corresponding to the primary RLCentity and the secondary RLC entity among the at least three RLCentities configured for the first bearer.

Specifically, for duplication transmission under a scenario of combiningDC and CA, a radio bearer may be configured with at least three RLCentities, and at least one RLC entity is configured corresponding toeach Cell Group (CG). The cell groups may be an MCG and an SCG, forexample.

In an implementation of the present disclosure, in a case thatduplication transmission of a first bearer is deactivated, it may fallback to split transmission, and a terminal device determines whether toperform split transmission or determine an RLC entity for transmitting aPDCP PDU according to cell groups corresponding to a primary RLC entityand a secondary RLC entity among at least three RLC entities configuredfor the first bearer. The terminal device may also determine an MACentity to which PDCP data volume pending for transmission is mappedaccording to cell groups corresponding to a primary RLC entity and asecondary RLC entity among at least three RLC entities configured forthe first bearer.

Optionally, the at least three RLC entities may include: one or moreprimary RLC entities or primary legs, one or more secondary RLC entitiesor secondary legs.

In addition, the at least three RLC entities may also include one ormore other RLC entities.

Optionally, in an implementation of the present disclosure, atransmitting PDCP entity may take the following contents as PDCP datavolume pending for transmission: a PDCP Service Data Unit (SDU) in whicha PDCP data PDU is not constructed; a PDCP data PDU not transmitted to alower layer; a PDCP control PDU; a PDCP SDU to be retransmitted for aDRB in a Acknowledged Mode (AM); a PDCP data PDU to be retransmitted fora DRB in a AM.

Optionally, the first bearer may be a DRB or an SRB.

Optionally, in an implementation of the present disclosure, a terminaldevice may receive configuration information of a network device for thefirst bearer, and determine the primary RLC entity and the secondary RLCentity among the at least three RLC entities according to theconfiguration information, and/or determine cell groups corresponding tothe primary RLC entity and the secondary RLC entity among the at leastthree RLC entities.

Optionally, the configuration information may include at least one pieceof the following information: an identifier of the first bearer; an RLCentity identifier, such as an identifier of at least one RLC entityamong the at least three RLC entities; an LCH identifier; a Cell groupidentifier, such as identifiers of at least two cell groups configuredfor the first bearer, wherein each of the at least two cell groups isconfigured with at least one RLC entity, or a corresponding or mappedcell group identifier is configured for an RLC entity when the RLCentity is configured; the number of RLC entities, such as 3 or 4, ormore; a threshold for uplink data split transmission, for example, auplink split data threshold (ul-DataSplitThreshold) and/or a uplinksplit data threshold of Rel-16 (ul-DataSplitThreshold-r16); a MAC entityidentifier; information of a primary RLC entity, including at least oneof an RLC entity identifier and a CG identifier; information of asecondary RLC entity, including at least one of an RLC entity identifierand a CG identifier; and indication information for indicating whetherthe primary RLC entity and the secondary RLC entity belong to the samecell group.

It should be noted that in the configuration information, the indicationinformation may explicitly indicate whether the primary RLC entity andthe secondary RLC entity belong to the same cell group. For example, itis indicated by 1 bit, wherein “0” indicates that the primary RLC entityand the secondary RLC entity belong to the same cell group, and “1”indicates that the primary RLC entity and the secondary RLC entity donot belong to the same cell group. In addition, in the configurationinformation, the indication information may implicitly indicate whetherthe primary RLC entity and the secondary RLC entity belong to the samecell group by configuration. For example, when configuring aprimary/secondary RLC entity, a CG identifier corresponding to an RLCentity is indicated. For example, as long as a secondary RLC entity isconfigured, a primary RLC entity and the secondary RLC entity are usedfor split transmission. In another example, as long as a secondary RLCentity is configured and the secondary RLC entity and a primary RLCentity are not of the same MAC entity, split transmission is performedby the primary RLC entity and the secondary RLC entity.

Optionally, in an implementation of the present disclosure, informationof an RLC entity may be an identifier of an RLC entity, or may be anidentification bit for identifying a primary RLC entity or a secondaryRLC entity.

Optionally, the configuration information for the first bearer iscarried in at least one of the following signaling: Media access controlelement (MAC CE), Downlink Control Information (DCI), and Radio ResourceControl (RRC) signaling.

At least three RLC entities configured for the first bearer will bespecifically described with reference to examples shown in FIGS. 4 to 7. As shown in FIG. 4 , the first bearer is DRB 1, which is configuredwith four RLC entities, namely, a primary RLC entity, RLC entity 1, RLCentity 2, and a secondary RLC entity. The primary RLC entity and the RLCentity 1 correspond to a primary MAC entity, which corresponds to anMCG, while the RLC entity 2 and the secondary RLC entity correspond to asecondary MAC entity, which corresponds to an SCG. As shown in FIG. 5 ,the first bearer is DRB 1, which is configured with four RLC entities,namely a primary RLC entity, RLC entity 1, RLC entity 2, and a secondaryRLC entity. The primary RLC entity, the RLC entity 1, and the RLC entity2 correspond to a primary MAC entity, which corresponds to an MCG, andthe secondary RLC entity corresponds to a secondary MAC entity, whichcorresponds to an SCG. As shown in FIG. 6 , the first bearer is DRB 1,which is configured with four RLC entities, namely, a primary RLCentity, RLC entity 1, RLC entity 2, and a secondary RLC entity. Theprimary RLC entity corresponds to a primary MAC entity, whichcorresponds to an MCG, the RLC entity 1 corresponds to MAC entity 1, theRLC entity 2 corresponds to MAC entity 2, and the secondary RLC entitycorresponds to a secondary MAC entity, which corresponds to an SCG. Asshown in FIG. 7 , the first bearer is DRB 1, which is configured withthree RLC entities, namely a primary RLC entity, RLC entity 1, and asecondary RLC entity. The primary RLC entity and the RLC entity 1correspond to a primary MAC entity, which corresponds to an MCG, and thesecondary RLC entity corresponds to a secondary MAC entity, whichcorresponds to an SCG.

It should be noted that the FIGS. 4 to 7 are only examples, and do notlimit the number of RLC entities and MAC entities in an implementationof the present disclosure. In addition, RLC entities and MAC entitiesmay have a one-to-one relationship or a many-to-one relationship, whichis not limited by an implementation of the present disclosure.

Optionally, in an implementation of the present disclosure, the terminaldevice may receive indication information of a network device for thefirst bearer, and determine cell groups corresponding to the primary RLCentity and the secondary RLC entity among the at least three RLCentities according to the indication information, or determine a cellgroup corresponding to an RLC entity used for split transmission amongthe at least three RLC entities.

For example, the indication information is used to indicate that an RLCentity corresponding to a cell group different from a cell groupcorresponding to the primary RLC entity in at least two cell groupsconfigured for the first bearer is a secondary RLC entity.

For another example, the indication information is used to indicate thatin an RLC entity corresponding to a cell group which is the same as acell group corresponding to the primary RLC entity is at least two cellgroups configured for the first bearer a secondary RLC entity.

For another example, the indication information is used to indicate thatonly an RLC entity corresponding to a cell group different from a cellgroup corresponding to the primary RLC entity in at least two cellgroups configured for the first bearer is a secondary RLC entity.

For another example, the indication information is used to indicate thatonly an RLC entity corresponding to a cell group which is the same as acell group corresponding to the primary RLC entity in at least two cellgroups configured for the first bearer is a secondary RLC entity.

For another example, the indication information is used to indicate thatan RLC entity corresponding to a cell group which is the same as ordifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity.

Optionally, in an implementation of the present disclosure, theindication information is used to indicate an RLC entity correspondingto split transmission among the at least three RLC entities, or toindicate a secondary RLC entity corresponding to split transmissionamong the at least three RLC entities, or to indicate whether an RLCentity among the at least three RLC entities meets split transmission.

For example, a secondary RLC entity configured for the first bearercorresponds to a CG different from a CG corresponding to a primary RLCentity, and a secondary RLC entity indicated by the indicationinformation corresponds to the same CG as a primary RLC entity, thensplit transmission cannot be performed.

For another example, a secondary RLC entity configured for the firstbearer corresponds to the same CG as a primary RLC entity, and asecondary RLC entity indicated by the indication information correspondsto a CG different from a CG corresponding to a primary RLC entity, thensplit transmission cannot be performed.

In another example, a secondary RLC entity configured for the firstbearer corresponds to a CG different from a CG corresponding to aprimary RLC entity, and a secondary RLC entity indicated by theindication information corresponds to a CG different from a CGcorresponding to a primary RLC entity, then split transmission can beperformed.

For another example, a secondary RLC entity configured for the firstbearer corresponds to the same CG as a primary RLC entity, and asecondary RLC entity indicated by the indication information correspondsto the same CG as a primary RLC entity, then split transmission can beperformed.

In an implementation of the present disclosure, the indicationinformation may be specifically indicated in the following manner iffirst signaling carries the indication information, or a value of theindication information is a first value, the indication information isused to indicate that an RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity; or, if the indication information is not carried in firstsignaling or a value of the indication information is a second value,the indication information is used to indicate that an RLC entitycorresponding to a cell group which is the same as a cell groupcorresponding to the primary RLC entity in at least two cell groupsconfigured for the first bearer is a secondary RLC entity; or, if firstsignaling carries the indication information or a value of theindication information is a first value, the indication information isused to indicate that only an RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity; or, if first signaling carries the indication information,or a value of the indication information is a first value, theindication information is used to indicate that only an RLC entitycorresponding to a cell group which is the same as a cell groupcorresponding to the primary RLC entity in at least two cell groupsconfigured for the first bearer is a secondary RLC entity; or, if theindication information is not carried in first signaling, or a value ofthe indication information is a second value, the indication informationis used to indicate that an RLC entity corresponding to a cell groupwhich is the same as or different from a cell group corresponding to theprimary RLC entity in at least two cell groups configured for the firstbearer is a secondary RLC entity.

In an implementation of the present disclosure, the indicationinformation may be specifically indicated in the following manner if theindication information is not carried in first signaling, or a value ofthe indication information is a first value, the indication informationis used to indicate that an RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity; or, if first signaling carries the indication information ora value of the indication information is a second value, the indicationinformation is used to indicate that an RLC entity corresponding to acell group which is the same as a cell group corresponding to theprimary RLC entity in at least two cell groups configured for the firstbearer is a secondary RLC entity; or, if the indication information isnot carried in first signaling, or a value of the indication informationis a first value, the indication information is used to indicate thatonly an RLC entity corresponding to a cell group different from a cellgroup corresponding to the primary RLC entity in at least two cellgroups configured for the first bearer is a secondary RLC entity; or, ifthe indication information is not carried in first signaling, or a valueof the indication information is a first value, the indicationinformation is used to indicate that only one RLC entity correspondingto a cell group which is the same as a cell group corresponding to theprimary RLC entity in at least two cell groups configured for the firstbearer is a secondary RLC entity; or, if first signaling carries theindication information, or a value of the indication information is asecond value, the indication information is used to indicate that an RLCentity corresponding to a cell group which is the same as or differentfrom a cell group corresponding to the primary RLC entity in at leasttwo cell groups configured for the first bearer is a secondary RLCentity.

Optionally, the indication information occupies a resource of 1 bit,wherein the first value is 1 and the second value is 0, or the firstvalue is 0 and the second value is 1.

Optionally, the first signaling is at least one of the followingsignaling: MAC CE, DCI, and RRC signaling.

Optionally, the indication information is configured throughconfiguration information for the first bearer, or configured for aterminal device, or configured for a cell group.

It should be noted that the indication information may not be limited tobe for the first bearer, for example, the indication information may befor the terminal device, or the indication information may be for a MACentity or a cell group.

Optionally, in the implementation of the present disclosure, as shown inFIGS. 8 and 9 , in the above act S210, the terminal device determines anRLC entity for transmitting the PDCP PDU according to the cell groupscorresponding to the primary RLC entity and the secondary RLC entityamong the at least three RLC entities configured for the first bearer,which may specifically include at least one of the following: if theprimary RLC entity and the secondary RLC entity correspond to differentcell groups, the terminal device determines to use the primary RLCentity and the secondary RLC entity to transmit the PDCP PDU throughsplit transmission, or the terminal device transmits the PDCP PDU to theprimary RLC entity and the secondary RLC entity; if the primary RLCentity and the secondary RLC entity correspond to the same cell group,the terminal device determines to use the primary RLC entity or thesecondary RLC entity to transmit the PDCP PDU, or the terminal devicetransmits the PDCP PDU to the primary RLC entity or the secondary RLCentity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group, the terminal device determines to usea first RLC entity and a second RLC entity to transmit the PDCP PDUthrough split transmission, or the terminal device transmits the PDCPPDU to the first RLC entity and the second RLC entity; if the primaryRLC entity and the secondary RLC entity correspond to the same cellgroup and a condition for split transmission is met, the terminal devicedetermines to use a first RLC entity and a second RLC entity to transmitthe PDCP PDU through split transmission, or the terminal devicetransmits the PDCP PDU to a first RLC entity and a second RLC entity; ifthe primary RLC entity and the secondary RLC entity correspond to thesame cell group and a condition for split transmission is not met, theterminal device determines to use the primary RLC entity or thesecondary RLC entity to transmit the PDCP PDU, or the terminal devicetransmits the PDCP PDU to the primary RLC entity or the secondary RLCentity; if a cell group which is the same as a cell group correspondingto the primary RLC entity in at least two cell groups configured for thefirst bearer only corresponds to one RLC entity and the one RLC entityis the primary RLC entity, the terminal device determines to use theprimary RLC entity to transmit the PDCP PDU, or the terminal devicetransmits the PDCP PDU to the primary RLC entity; if there is only oneRLC entity in a MAC entity where the primary RLC entity is located, theterminal device determines that an RLC entity corresponding to a cellgroup different from a cell group corresponding to the primary RLCentity is the secondary RLC entity, and the terminal device determinesto use the primary RLC entity and the secondary RLC entity to transmitthe PDCP PDU through split transmission, or the terminal devicetransmits the PDCP PDU to the primary RLC entity and the secondary RLCentity; if there are multiple RLC entities in a MAC entity where theprimary RLC entity is located, and there is an RLC entity in a MACentity different from the MAC entity where the primary RLC entity islocated, the terminal device determines that an RLC entity correspondingto a cell group different from a cell group corresponding to the primaryRLC entity is the secondary RLC entity, and the terminal devicedetermines to use the primary RLC entity and the secondary RLC entity totransmit the PDCP PDU through split transmission, or the terminal devicetransmits the PDCP PDU to the primary RLC entity and the secondary RLCentity.

It should be noted that in a case that a terminal device receivesindication information for the first bearer sent by a network device, orin a case that a terminal device receives indication information for thefirst bearer sent by a network device and it is indicated that theprimary RLC entity and the secondary RLC entity correspond to one CG, ifa cell group which is the same as a cell group corresponding to theprimary RLC entity in at least two cell groups configured for the firstbearer only corresponds to one RLC entity, and the one RLC entity is theprimary RLC entity, the terminal device determines to use the primaryRLC entity to transmit a PDCP PDU, or the terminal device transmits aPDCP PDU to the primary RLC entity.

Optionally, in an implementation of the present disclosure, as shown inFIG. 10 and FIG. 11 , in the above act S210, the terminal devicedetermines the MAC entity to which the PDCP data volume pending fortransmission is mapped according to the cell groups corresponding to theprimary RLC entity and the secondary RLC entity among the at least threeRLC entities configured for the first bearer, including at least one ofthe following: if the primary RLC entity and the secondary RLC entitycorrespond to different cell groups, the terminal device maps the PDCPdata volume pending for transmission to a MAC entity corresponding tothe primary RLC entity and a MAC entity corresponding to the secondaryRLC entity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group, the terminal device maps the PDCPdata volume pending for transmission to a MAC entity corresponding tothe primary RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group, the terminal device maps thePDCP data volume pending for transmission to a MAC entity correspondingto the primary RLC entity and maps 0 to a MAC entity corresponding tothe secondary RLC entity; if the primary RLC entity and the secondaryRLC entity correspond to the same cell group, the terminal device mapsthe PDCP data volume pending for transmission to a MAC entitycorresponding to a first RLC entity and a MAC entity corresponding to asecond RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is met, the terminal device maps the PDCP data volumepending for transmission to a MAC entity corresponding to a first RLCentity and a MAC entity corresponding to a second RLC entity; if theprimary RLC entity and the secondary RLC entity correspond to the samecell group, the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity anda MAC entity corresponding to the secondary RLC entity; if the primaryRLC entity and the secondary RLC entity correspond to the same cellgroup and a condition for split transmission is met, the terminal devicemaps the PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity and a MAC entity correspondingto the secondary RLC entity; if the primary RLC entity and the secondaryRLC entity correspond to the same cell group and a condition for splittransmission is not met, the terminal device maps the PDCP data volumepending for transmission to a MAC entity corresponding to the primaryRLC entity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group and a condition for split transmissionis not met, the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity andmaps 0 to a MAC entity corresponding to the secondary RLC entity; if acell group which is the same as a cell group corresponding to theprimary RLC entity in at least two cell groups configured for the firstbearer only corresponds to one RLC entity, and the one RLC entity is theprimary RLC entity, the terminal device determines to use the primaryRLC entity to transmit a PDCP PDU, or the terminal device maps the PDCPdata volume pending for transmission to a MAC entity corresponding tothe primary RLC entity; if there is only one RLC entity in a MAC entitywhere the primary RLC entity is located, the terminal device determinesthat an RLC entity corresponding to a cell group different from a cellgroup corresponding to the primary RLC entity is the secondary RLCentity, and the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity anda MAC entity corresponding to the secondary RLC entity; if there aremultiple RLC entities in a MAC entity where the primary RLC entity islocated, and there is an RLC entity in a MAC entity different from theMAC entity where the primary RLC entity is located, the terminal devicedetermines that an RLC entity corresponding to a cell group differentfrom a cell group corresponding to the primary RLC entity is thesecondary RLC entity, and the terminal device maps the PDCP data volumepending for transmission to a MAC entity corresponding to the primaryRLC entity and a MAC entity corresponding to the secondary RLC entity.

It should be noted that in a case that a terminal device receivesindication information for the first bearer sent by a network device, orin a case that a terminal device receives indication information for thefirst bearer sent by a network device and it is indicated that a primaryRLC entity and a secondary RLC entity correspond to one CG, if a cellgroup which is the same as a cell group corresponding to the primary RLCentity in at least two cell groups configured for the first bearer onlycorresponds to one RLC entity, and the one RLC entity is the primary RLCentity, the terminal device determines to use the primary RLC entity totransmit a PDCP PDU, or the terminal device maps the PDCP data volumepending for transmission to a MAC entity corresponding to the primaryRLC entity.

Optionally, in a specific implementation of the act S210, the first RLCentity and the second RLC entity correspond to different cell groups.

Optionally, the first RLC entity and the second RLC entity may met thefollowing conditions: the first RLC entity is the primary RLC entity,and the second RLC entity is a specific RLC entity corresponding to acell group different from a cell group corresponding to the first RLCentity; or, the first RLC entity is the secondary RLC entity, and thesecond RLC entity is a specific RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the first RLC entity; or,the first RLC entity is the secondary RLC entity and the second RLCentity is the primary RLC entity; or, the first RLC entity is theprimary RLC entity, and the second RLC entity is the secondary RLCentity.

Optionally, in a specific implementation of the act S210, the specificRLC entity is one of the following: any one RLC entity, an RLC entitywith the smallest index identifier, an RLC entity with the largest indexidentifier, an RLC entity with the best channel quality, and anindicated RLC entity.

Optionally, in a specific implementation of the act S210, the conditionfor split transmission includes that the data volume pending fortransmission corresponding to the first bearer is greater than or equalto a threshold.

Optionally, the data volume pending for transmission corresponding tothe first bearer is one of the following: in all RLC entities configuredfor the first bearer, a total amount of PDCP data volume and RLC datavolume pending for initial transmission; in an activated RLC entityconfigured for the first bearer, a total amount of PDCP data volume andRLC data volume pending for initial transmission; in an RLC entity thathad been activated and is configured for the first bearer, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer and has data pending for transmission, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer for initial transmission of data, a total amount ofPDCP data volume and RLC data volume pending for initial transmission; atotal amount of PDCP data volume and RLC data volume pending for initialtransmission in the primary RLC entity and the secondary RLC entity; atotal amount of PDCP data volume and RLC data volume pending fortransmission in the primary RLC entity and the secondary RLC entity.

Therefore, in an implementation of the present disclosure, in a casethat duplication transmission of the first bearer is deactivated,according to cell groups corresponding to a primary RLC entity and asecondary RLC entity among at least three RLC entities configured forthe first bearer, a terminal device may determine an RLC entity fortransmitting a PDCP PDU, and/or determine a MAC entity to which PDCPdata volume pending for transmission is mapped.

Further, when a primary RLC entity and a secondary RLC entity belong tothe same cell group, split transmission is not used.

Or, when a primary RLC entity and a secondary RLC entity belong to thesame cell group and a condition for split transmission is met, two RLCentities belonging to different cell groups are selected for splittransmission. It may be ensured that there are more resources totransmit PDCP PDUs when data volume is large.

The wireless communication method according to an implementation of thepresent disclosure is described in detail above from a perspective of aterminal device in connection with FIG. 3 to FIG. 11 . In the following,a wireless communication method according to another implementation ofthe present disclosure will be described in detail from anotherperspective of a terminal device in connection with FIG. 12 . It shouldbe understood that the description in FIG. 12 corresponds to thedescription of FIGS. 3 to 11 , and a similar description may refer tothe above description, which will not be repeated here to avoidrepetition.

FIG. 12 is a schematic flow chart of a wireless communication method 300provided according to an implementation of the present disclosure. Themethod 300 may be performed by a terminal device in the communicationsystem shown in FIG. 1 . As shown in FIG. 12 , the method 300 mayinclude at least part of following contents.

In S310, in a case that duplication transmission of a first bearer isdeactivated, a terminal device determines cell groups corresponding to aprimary RLC entity and a secondary RLC entity among at least three RLCentities configured for the first bearer according to indicationinformation for the first bearer.

In S320, the terminal device determines an RLC entity for transmitting aPDCP PDU according to the cell groups corresponding to the primary RLCentity and the secondary RLC entity among the at least three RLCentities, and/or the terminal device determines or indicates PDCP datavolume pending for transmission.

Optionally, in S320, the terminal device may determine or indicate thePDCP data volume pending for transmission according to the cell groupscorresponding to the primary RLC entity and the secondary RLC entityamong the at least three RLC entities.

Further, in S320, the terminal device may determine or indicate a MACentity to which the PDCP data volume pending for transmission is mappedaccording to the cell groups corresponding to the primary RLC entity andthe secondary RLC entity among the at least three RLC entities.

Optionally, in some implementations, the terminal device may alsodetermine a primary RLC entity and a secondary RLC entity among at leastthree RLC entities configured for a first bearer according to indicationinformation for the first bearer.

Optionally, in some implementations, the indication information is usedto indicate an RLC entity corresponding to split transmission among theat least three RLC entities, or to indicate a secondary RLC entitycorresponding to split transmission among the at least three RLCentities, or to indicate whether an RLC entity among the at least threeRLC entities meets split transmission.

It should be noted that the indication information may not be limited tobe for the first bearer, for example, the indication information may befor the terminal device, or the indication information may be for a MACentity or a cell group.

Optionally, in some implementations, if first signaling carries theindication information, or a value of the indication information is afirst value, the indication information is used to indicate that an RLCentity corresponding to a cell group different from a cell groupcorresponding to the primary RLC entity in at least two cell groupsconfigured for the first bearer is a secondary RLC entity; or, if theindication information is not carried in first signaling, or a value ofthe indication information is a second value, the indication informationis used to indicate that an RLC entity corresponding to a cell groupwhich is the same as a cell group corresponding to the primary RLCentity in at least two cell groups configured for the first bearer is asecondary RLC entity; or, if first signaling carries the indicationinformation, or a value of the indication information is a first value,the indication information is used to indicate that only an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity in at least two cell groups configured for thefirst bearer is a secondary RLC entity; or, if the indicationinformation is not carried in first signaling, or a value of theindication information is a second value, the indication information isused to indicate that an RLC entity corresponding to a cell group whichis the same as or different from a cell group corresponding to theprimary RLC entity in at least two cell groups configured for the firstbearer is a secondary RLC entity.

Optionally, in some implementations, if the indication information isnot carried in first signaling, or a value of the indication informationis a first value, the indication information is used to indicate that anRLC entity corresponding to a cell group different from a cell groupcorresponding to the primary RLC entity in at least two cell groupsconfigured for the first bearer is a secondary RLC entity; or, if theindication information is carried in first signaling or a value of theindication information is a second value, the indication information isused to indicate that an RLC entity corresponding to a cell group whichis the same as a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity; or, if the indication information is not carried in firstsignaling, or a value of the indication information is a first value,the indication information is used to indicate that only an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity in at least two cell groups configured for thefirst bearer is a secondary RLC entity; or, if first signaling carriesthe indication information, or a value of the indication information isa second value, the indication information is used to indicate that anRLC entity corresponding to a cell group which is the same as ordifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity.

Optionally, the indication information occupies a resource of 1 bit,wherein the first value is 1 and the second value is 0, or the firstvalue is 0 and the second value is 1.

Optionally, the first signaling is at least one of the followingsignaling: MAC CE, DCI, and RRC signaling.

Optionally, the indication information is configured throughconfiguration information for the first bearer, or configured for theterminal device, or configured for a cell group.

Optionally, in some implementations, in the act S320, the terminaldevice determines the RLC entity for transmitting the PDCP PDU accordingto the cell groups corresponding to the primary RLC entity and thesecondary RLC entity among the at least three RLC entities, which mayspecifically include at least one of the following: if the primary RLCentity and the secondary RLC entity correspond to different cell groups,the terminal device determines to use the primary RLC entity and thesecondary RLC entity to transmit a PDCP PDU through split transmission,or the terminal device transmits a PDCP PDU to the primary RLC entityand the secondary RLC entity; if the primary RLC entity and thesecondary RLC entity correspond to the same cell group, the terminaldevice determines to use the primary RLC entity or the secondary RLCentity to transmit a PDCP PDU, or the terminal device transmits a PDCPPDU to the primary RLC entity or the secondary RLC entity; if theprimary RLC entity and the secondary RLC entity correspond to the samecell group, the terminal device determines to use a first RLC entity anda second RLC entity to transmit a PDCP PDU through split transmission,or the terminal device transmits a PDCP PDU to a first RLC entity and asecond RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is met, the terminal device determines to use a first RLCentity and a second RLC entity to transmit a PDCP PDU through splittransmission, or the terminal device transmits a PDCP PDU to a first RLCentity and a second RLC entity; if the primary RLC entity and thesecondary RLC entity correspond to the same cell group and a conditionfor split transmission is not met, the terminal device determines to usethe primary RLC entity or the secondary RLC entity to transmit a PDCPPDU, or the terminal device transmits a PDCP PDU to the primary RLCentity or the secondary RLC entity; if a cell group which is the same asa cell group corresponding to the primary RLC entity in at least twocell groups configured for the first bearer only corresponds to one RLCentity and the one RLC entity is the primary RLC entity, the terminaldevice determines to use the primary RLC entity to transmit a PDCP PDU,or the terminal device transmits a PDCP PDU to the primary RLC entity;if there is only one RLC entity in a MAC entity where the primary RLCentity is located, the terminal device determines that an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity is the secondary RLC entity, and the terminaldevice determines to use the primary RLC entity and the secondary RLCentity to transmit a PDCP PDU through split transmission, or theterminal device transmits a PDCP PDU to the primary RLC entity and thesecondary RLC entity; if there are multiple RLC entities in a MAC entitywhere the primary RLC entity is located, and there is an RLC entity in aMAC entity different from the MAC entity where the primary RLC entity islocated, the terminal device determines that an RLC entity correspondingto a cell group different from a cell group corresponding to the primaryRLC entity is the secondary RLC entity, and the terminal devicedetermines to use the primary RLC entity and the secondary RLC entity totransmit a PDCP PDU through split transmission, or the terminal devicetransmits a PDCP PDU to the primary RLC entity and the secondary RLCentity.

Optionally, in some implementations, in the act S320, the terminaldevice determines the MAC entity to which the PDCP data volume pendingfor transmission is mapped according to the cell groups corresponding tothe primary RLC entity and the secondary RLC entity among the at leastthree RLC entities, which may specifically include at least one of thefollowing: the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity anda MAC entity corresponding to the secondary RLC entity if the primaryRLC entity and the secondary RLC entity correspond to different cellgroups; the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity ifthe primary RLC entity and the secondary RLC entity correspond to thesame cell group; the terminal device maps the PDCP data volume pendingfor transmission to a MAC entity corresponding to the primary RLC entityand maps 0 to a MAC entity corresponding to the secondary RLC entity ifthe primary RLC entity and the secondary RLC entity correspond to thesame cell group; the terminal device maps the PDCP data volume pendingfor transmission to a MAC entity corresponding to a first RLC entity anda MAC entity corresponding to a second RLC entity if the primary RLCentity and the secondary RLC entity correspond to the same cell group;the terminal device maps the PDCP data volume pending for transmissionto a MAC entity corresponding to a first RLC entity and a MAC entitycorresponding to a second RLC entity if the primary RLC entity and thesecondary RLC entity correspond to the same cell group and a conditionfor split transmission is met; the terminal device maps the PDCP datavolume pending for transmission to a MAC entity corresponding to theprimary RLC entity and a MAC entity corresponding to the secondary RLCentity if the primary RLC entity and the secondary RLC entity correspondto the same cell group; the terminal device maps the PDCP data volumepending for transmission to a MAC entity corresponding to the primaryRLC entity and a MAC entity corresponding to the secondary RLC entity ifthe primary RLC entity and the secondary RLC entity correspond to thesame cell group and a condition for split transmission is met; theterminal device maps the PDCP data volume pending for transmission to aMAC entity corresponding to the primary RLC entity if the primary RLCentity and the secondary RLC entity correspond to the same cell groupand a condition for split transmission is not met; the terminal devicemaps the PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity and maps 0 to a MAC entitycorresponding to the secondary RLC entity if the primary RLC entity andthe secondary RLC entity correspond to the same cell group and acondition for split transmission is not met; if a cell group which isthe same as a cell group corresponding to the primary RLC entity in atleast two cell groups configured for the first bearer only correspondsto one RLC entity and the one RLC entity is the primary RLC entity, theterminal device determines to use the primary RLC entity to transmit aPDCP PDU, or the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity; ifthere is only one RLC entity in a MAC entity where the primary RLCentity is located, the terminal device determines that an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity is the secondary RLC entity, and the terminaldevice maps the PDCP data volume pending for transmission to a MACentity corresponding to the primary RLC entity and a MAC entitycorresponding to the secondary RLC entity; if there are multiple RLCentities in a MAC entity where the primary RLC entity is located, andthere is an RLC entity in a MAC entity different from the MAC entitywhere the primary RLC entity is located, the terminal device determinesthat an RLC entity corresponding to a cell group different from a cellgroup corresponding to the primary RLC entity is the secondary RLCentity, and the terminal device maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity anda MAC entity corresponding to the secondary RLC entity.

Optionally, the first RLC entity and the second RLC entity correspond todifferent cell groups.

Optionally, the first RLC entity and the second RLC entity may meet thefollowing condition: the first RLC entity is the primary RLC entity, andthe second RLC entity is a specific RLC entity corresponding to a cellgroup different from a cell group corresponding to the first RLC entity;or, the first RLC entity is the secondary RLC entity, and the second RLCentity is a specific RLC entity corresponding to a cell group differentfrom a cell group corresponding to the first RLC entity; or, the firstRLC entity is the secondary RLC entity and the second RLC entity is theprimary RLC entity; or, the first RLC entity is the primary RLC entity,and the second RLC entity is the secondary RLC entity.

Optionally, the specific RLC entity is one of the following: any one RLCentity, an RLC entity with the smallest index identifier, an RLC entitywith the largest index identifier, an RLC entity with the best channelquality, and an indicated RLC entity.

Optionally, the condition for split transmission includes that datavolume pending for transmission corresponding to the first bearer isgreater than or equal to a threshold.

Optionally, the data volume pending for transmission corresponding tothe first bearer is one of the following: in all RLC entities configuredfor the first bearer, a total amount of PDCP data volume and RLC datavolume pending for initial transmission; in an activated RLC entityconfigured for the first bearer, a total amount of PDCP data volume andRLC data volume pending for initial transmission; in an RLC entity thathad been activated and is configured for the first bearer, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer and has data pending for transmission, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer for initial transmission of data, a total amount ofPDCP data volume and RLC data volume pending for initial transmission; atotal amount of PDCP data volume and RLC data volume pending for initialtransmission in the primary RLC entity and the secondary RLC entity; atotal amount of PDCP data volume and RLC data volume pending fortransmission in the primary RLC entity and the secondary RLC entity.

Optionally, in some implementations, the terminal device determines cellgroups corresponding to the primary RLC entity and the secondary RLCentity among the at least three RLC entities according to configurationinformation for the first bearer.

Optionally, the configuration information includes at least one of thefollowing: an identifier of the first bearer, an identifier of an RLCentity, an LCH identifier, an identifier of a cell group, the number ofRLC entities, a threshold of uplink data split transmission, anidentifier of a MAC entity, information of a primary RLC entity, andinformation of a secondary RLC entity, and indication information forindicating whether the primary RLC entity and the secondary RLC entitybelong to the same cell group.

Optionally, in an implementation of the present disclosure, informationof an RLC entity may be an identifier of an RLC entity, or may be anidentification bit for identifying a primary RLC entity or a secondaryRLC entity.

Optionally, the configuration information is carried in at least one ofthe following signaling: MAC CE, DCI, and RRC signaling.

Therefore, in an implementation of the present disclosure, in a casethat duplication transmission of a first bearer is deactivated, aterminal device may determine cell groups corresponding to a primary RLCentity and a secondary RLC entity among at least three RLC entitiesconfigured for the first bearer based on indication information for thefirst bearer sent by a network device, and further determine an RLCentity for transmitting a PDCP PDU, and/or, determine a MAC entity towhich PDCP data volume pending for transmission is mapped.

Further, when a primary RLC entity and a secondary RLC entity belong tothe same cell group, split transmission is not used.

Or, when a primary RLC entity and a secondary RLC entity belong to thesame cell group and a condition for split transmission is met, two RLCentities belonging to different cell groups are selected for splittransmission. It may be ensured that there are more resources totransmit PDCP PDUs when data volume is large.

With reference to FIGS. 3 to 11 , the wireless communication methodaccording to an implementation of the present disclosure is described indetail from a perspective of a terminal device. It should be understoodthat the description in FIG. 13 corresponds to the description in FIGS.3 to 11 , and a similar description may refer to the above description,which will not be repeated here to avoid repetition.

FIG. 13 is a schematic flow chart of a wireless communication method 400provided according to an implementation of the present disclosure. Themethod 400 may be performed by a terminal device in the communicationsystem shown in FIG. 1 . As shown in FIG. 13 , the method 400 mayinclude at least part of following contents.

In S410, in a case that duplication transmission of a first bearer isdeactivated and there is no secondary RLC entity or no secondary RLCentity is configured among at least three RLC entities configured forthe first bearer, a terminal device determines whether to carry outsplit transmission, or a terminal device determines an RLC entity fortransmitting a PDCP PDU.

Optionally, in the act S410, the terminal device determines the RLCentity for transmitting the PDCP PDU, which may specifically include oneof the following: the terminal device determines to use a primary RLCentity among the at least three RLC entities to transmit a PDCP PDU, orthe terminal device transmits a PDCP PDU to a primary RLC entity; if acondition for split transmission is met, the terminal device determinesto use a first RLC entity and a second RLC entity among the at leastthree RLC entities to transmit a PDCP PDU through split transmission, orthe terminal device transmits a PDCP PDU to a first RLC entity and asecond RLC entity among the at least three RLC entities; if a conditionfor split transmission is not met, the terminal device determines to usea primary RLC entity among the at least three RLC entities to transmit aPDCP PDU, or the terminal device transmits a PDCP PDU to the primary RLCentity.

Optionally, the first RLC entity and the second RLC entity correspond todifferent cell groups. In addition, the first RLC entity and the secondRLC entity may correspond to the same cell group.

Optionally, descriptions of the first RLC entity and the second RLCentity may refer to the example in the method 200.

Optionally, in an implementation of the present disclosure, the terminaldevice may receive first indication information of a network device forthe first bearer, and determine cell groups corresponding to the firstRLC entity and the second RLC entity according to the first indicationinformation, or determine whether the first RLC entity and the secondRLC entity correspond to the same cell group.

It should be noted that the first indication information may not belimited to be for the first bearer, for example, the first indicationinformation may be for a terminal device, or the first indicationinformation may be for a MAC entity or a cell group.

Optionally, the first indication information is at least one of thefollowing signaling: MAC CE, DCI, and RRC signaling.

Optionally, in an implementation of the present disclosure, the terminaldevice may receive second indication information of a network device forthe first bearer, and determine, according to the second indicationinformation, that in a case that there is no secondary RLC entity or nosecondary RLC entity is configured, according to the second indicationinformation, the terminal device determines whether to use splittransmission or transmit a PDCP PDU to multiple RLC entities.

It should be noted that the second indication information may not belimited to be for the first bearer, for example, the second indicationinformation may be for a terminal device, or the second indicationinformation may be for a MAC entity or a cell group.

Optionally, the second indication information is carried in at least oneof the following signaling: MAC CE, DCI, and RRC signaling.

Optionally, the first indication information and the second indicationinformation may be carried in the same signaling or different signaling,which is not limited by the present disclosure.

In an implementation of the present disclosure, the first indicationinformation may be specifically indicated in the following manner if thefirst indication information is carried in first signaling or a value ofthe first indication information is a first value, the first indicationinformation is used to indicate that a first RLC entity and a second RLCentity in at least two cell groups configured for the first bearercorrespond to different cell groups; or, if the first indicationinformation is not carried in first signaling or a value of the firstindication information is a second value, the first indicationinformation is used to indicate that a first RLC entity and a second RLCentity in at least two cell groups configured for the first bearercorrespond to the same cell group.

In an implementation of the present disclosure, the first indicationinformation may be specifically indicated in the following manner if thefirst indication information is not carried in first signaling or avalue of the first indication information is a first value, the firstindication information is used to indicate that a first RLC entity and asecond RLC entity in at least two cell groups configured for the firstbearer correspond to different cell groups; or if the first indicationinformation is carried in first signaling or a value of the firstindication information is a second value, the first indicationinformation is used to indicate that a first RLC entity and a second RLCentity in at least two cell groups configured for the first bearercorrespond to the same cell group.

Optionally, the first indication information occupies a resource of 1bit, wherein the first value is 1 and the second value is 0, or thefirst value is 0 and the second value is 1.

Optionally, the first indication information is configured throughconfiguration information for the first bearer, or configured for aterminal device, or configured for a cell group.

Optionally, the first RLC entity is the primary RLC entity, and thesecond RLC entity is a specific RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the first RLC entity.

Optionally, the specific RLC entity is one of the following: any one RLCentity, an RLC entity with the smallest index identifier, an RLC entitywith the largest index identifier, an RLC entity with the best channelquality, and an indicated RLC entity.

Optionally, the condition for split transmission includes that datavolume pending for transmission corresponding to the first bearer isgreater than or equal to a threshold.

Optionally, the data volume pending for transmission corresponding tothe first bearer is one of the following: in all RLC entities configuredfor the first bearer, a total amount of PDCP data volume and RLC datavolume pending for initial transmission; in an activated RLC entityconfigured for the first bearer, a total amount of PDCP data volume andRLC data volume pending for initial transmission; in an RLC entity thathad been activated and is configured for the first bearer, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer and has data pending for transmission, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; and in an RLC entity that had been activated and isconfigured for the first bearer for initial transmission of data, atotal amount of PDCP data volume and RLC data volume pending for initialtransmission.

Optionally, in some implementations, the terminal device determines thatthere is no secondary RLC entity among the at least three RLC entitiesaccording to configuration information for the first bearer.

Optionally, the configuration information includes at least one of thefollowing: an identifier of the first bearer, an identifier of an RLCentity, an LCH identifier, an identifier of a cell group, the number ofRLC entities, a threshold of uplink data split transmission, anidentifier of a MAC entity, and information of a primary RLC entity.

Optionally, in an implementation of the present disclosure, informationof an RLC entity may be an identifier of an RLC entity, or may be anidentification bit for identifying a primary RLC entity or a secondaryRLC entity.

Optionally, the configuration information is carried in at least one ofthe following signaling: MAC CE, DCI, and RRC signaling.

Therefore, in an implementation of the present disclosure, a terminaldevice determines an RLC entity that transmits a PDCP PDU in a case thatduplication transmission of a first bearer is deactivated and there isno secondary RLC entity among at least three RLC entities configured forthe first bearer.

Method implementations of the present disclosure are described in detailabove with reference to FIG. 3 to FIG. 13 , apparatus implementations ofthe present disclosure will be described in detail below with referenceto FIG. 14 to FIG. 19 . It should be understood that the apparatusimplementations and the method implementations correspond to each other,and description of the method implementations may be referred to forsimilar description of the apparatus implementations.

FIG. 14 is a schematic block diagram of a terminal device 500 accordingto an implementation of the present disclosure. As shown in FIG. 14 ,the terminal device 500 includes a processing unit 510.

In a case that duplication transmission of a first bearer isdeactivated, the processing unit 510 is configured to determine an RLCentity for transmitting a PDCP PDU according to cell groupscorresponding to a primary RLC entity and a secondary RLC entity amongat least three RLC entities configured for the first bearer, and/or theprocessing unit 510 is configured to determine a MAC entity to whichPDCP data volume pending for transmission is mapped according to cellgroups corresponding to a primary RLC entity and a secondary RLC entityamong at least three RLC entities configured for the first bearer.

Optionally, the processing unit 510 is configured to determine the RLCentity for transmitting the PDCP PDU according to the cell groupscorresponding to the primary RLC entity and the secondary RLC entityamong the at least three RLC entities configured for the first bearer,including at least one of the following: if the primary RLC entity andthe secondary RLC entity correspond to different cell groups, theprocessing unit 510 is configured to determine to use the primary RLCentity and the secondary RLC entity to transmit a PDCP PDU through splittransmission, or to transmit a PDCP PDU to the primary RLC entity andthe secondary RLC entity; if the primary RLC entity and the secondaryRLC entity correspond to the same cell group, the processing unit 510 isconfigured to determine to use the primary RLC entity or the secondaryRLC entity to transmit a PDCP PDU, or to transmit a PDCP PDU to theprimary RLC entity or the secondary RLC entity; if the primary RLCentity and the secondary RLC entity correspond to the same cell group,the processing unit 510 is configured to determine to use a first RLCentity and a second RLC entity to transmit a PDCP PDU through splittransmission, or to transmit a PDCP PDU to a first RLC entity and asecond RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is met, the processing unit 510 is configured to determineto use a first RLC entity and a second RLC entity to transmit a PDCP PDUthrough split transmission, or to transmit a PDCP PDU to a first RLCentity and a second RLC entity; if the primary RLC entity and thesecondary RLC entity correspond to the same cell group and a conditionfor split transmission is not met, the processing unit 510 is configuredto determine to use the primary RLC entity or the secondary RLC entityto transmit a PDCP PDU, or to transmit a PDCP PDU to the primary RLCentity or the secondary RLC entity; if a cell group which is the same asa cell group corresponding to the primary RLC entity in at least twocell groups configured for the first bearer only corresponds to one RLCentity and the one RLC entity is the primary RLC entity, the processingunit 510 is configured to determine to use the primary RLC entity totransmit a PDCP PDU, or to transmit a PDCP PDU to the primary RLCentity; if there is only one RLC entity in a MAC entity where theprimary RLC entity is located, the processing unit 510 is configured todetermine that an RLC entity corresponding to a cell group differentfrom a cell group corresponding to the primary RLC entity is thesecondary RLC entity, and the processing unit 510 is configured todetermine to use the primary RLC entity and the secondary RLC entity totransmit a PDCP PDU through split transmission, or to transmit a PDCPPDU to the primary RLC entity and the secondary RLC entity; and if thereare multiple RLC entities in a MAC entity where the primary RLC entityis located, and there is an RLC entity in a MAC entity different fromthe MAC entity where the primary RLC entity is located, the processingunit 510 is configured to determine that an RLC entity corresponding toa cell group different from a cell group corresponding to the primaryRLC entity is the secondary RLC entity, and the processing unit 510 isconfigured to determine to use the primary RLC entity and the secondaryRLC entity to transmit a PDCP PDU through split transmission, or theprocessing unit 510 is configured to transmit a PDCP PDU to the primaryRLC entity and the secondary RLC entity.

Optionally, the processing unit 510 is configured to determine the MACentity to which the PDCP data volume pending for transmission is mappedaccording to the cell groups corresponding to the primary RLC entity andthe secondary RLC entity among the at least three RLC entitiesconfigured for the first bearer, including at least one of thefollowing: if the primary RLC entity and the secondary RLC entitycorrespond to different cell groups, the processing unit 510 isconfigured to map the PDCP data volume pending for transmission to a MACentity corresponding to the primary RLC entity and a MAC entitycorresponding to the secondary RLC entity; if the primary RLC entity andthe secondary RLC entity correspond to the same cell group, theprocessing unit 510 is configured to map the PDCP data volume pendingfor transmission to a MAC entity corresponding to the primary RLCentity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group, the processing unit 510 maps the PDCPdata volume pending for transmission to a MAC entity corresponding tothe primary RLC entity and a MAC entity corresponding to the secondaryRLC entity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group and a condition for split transmissionis met, the processing unit 510 maps the PDCP data volume pending fortransmission to a MAC entity corresponding to the primary RLC entity anda MAC entity corresponding to the secondary RLC entity; if the primaryRLC entity and the secondary RLC entity correspond to the same cellgroup, the processing unit 510 is configured to map the PDCP data volumepending for transmission to a MAC entity corresponding to the primaryRLC entity and map 0 to a MAC entity corresponding to the secondary RLCentity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group, the processing unit 510 is configuredto map the PDCP data volume pending for transmission to a MAC entitycorresponding to a first RLC entity and a MAC entity corresponding to asecond RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is met, the processing unit 510 is configured to map thePDCP data volume pending for transmission to a MAC entity correspondingto a first RLC entity and a MAC entity corresponding to a second RLCentity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group and a condition for split transmissionis not met, the processing unit 510 is configured to map the PDCP datavolume pending for transmission to a MAC entity corresponding to theprimary RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is not met, the processing unit 510 is configured to mapthe PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity and map 0 to a MAC entitycorresponding to the secondary RLC entity; if a cell group which is thesame as a cell group corresponding to the primary RLC entity in at leasttwo cell groups configured for the first bearer only corresponds to oneRLC entity and the one RLC entity is the primary RLC entity, theprocessing unit 510 is configured to determine to use the primary RLCentity to transmit a PDCP PDU, or the processing unit 510 is configuredto map the PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity; if there is only one RLC entityin a MAC entity where the primary RLC entity is located, the processingunit 510 is configured to determine that an RLC entity corresponding toa cell group different from a cell group corresponding to the primaryRLC entity is the secondary RLC entity, and the processing unit 510 isconfigured to map the PDCP data volume pending for transmission to a MACentity corresponding to the primary RLC entity and a MAC entitycorresponding to the secondary RLC entity; and if there are multiple RLCentities in a MAC entity where the primary RLC entity is located, andthere is an RLC entity in a MAC entity different from the MAC entitywhere the primary RLC entity is located, the processing unit 510 isconfigured to determine an RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the primary RLC entity asthe secondary RLC entity, and the processing unit 510 is configured tomap the PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity and a MAC entity correspondingto the secondary RLC entity.

Optionally, the first RLC entity and the second RLC entity correspond todifferent cell groups.

Optionally, the first RLC entity is the primary RLC entity, and thesecond RLC entity is a specific RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the first RLC entity; or,the first RLC entity is the secondary RLC entity, and the second RLCentity is a specific RLC entity corresponding to a cell group differentfrom a cell group corresponding to the first RLC entity; or, the firstRLC entity is the secondary RLC entity and the second RLC entity is theprimary RLC entity; or, the first RLC entity is the primary RLC entity,and the second RLC entity is the secondary RLC entity.

Optionally, the specific RLC entity is one of the following: any one RLCentity, an RLC entity with the smallest index identifier, an RLC entitywith the largest index identifier, an RLC entity with the best channelquality, and an indicated RLC entity.

Optionally, the condition for split transmission includes that datavolume pending for transmission corresponding to the first bearer isgreater than or equal to a threshold.

Optionally, the data volume pending for transmission corresponding tothe first bearer is one of the following: in all RLC entities configuredfor the first bearer, a total amount of PDCP data volume and RLC datavolume pending for initial transmission; in an activated RLC entityconfigured for the first bearer, a total amount of PDCP data volume andRLC data volume pending for initial transmission; in an RLC entity thathad been activated and is configured for the first bearer, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer and has data pending for transmission, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer for initial transmission of data, a total amount ofPDCP data volume and RLC data volume pending for initial transmission; atotal amount of PDCP data volume and RLC data volume pending for initialtransmission in the primary RLC entity and the secondary RLC entity; anda total amount of PDCP data volume and RLC data volume pending fortransmission in the primary RLC entity and the secondary RLC entity.

Optionally, the processing unit 510 is further configured to determinecell groups corresponding to the primary RLC entity and the secondaryRLC entity among the at least three RLC entities according toconfiguration information for the first bearer.

Optionally, the configuration information includes at least one of thefollowing: an identifier of the first bearer, an identifier of an RLCentity, a Logical Channel (LCH) identifier, an identifier of a cellgroup, the number of RLC entities, a threshold of uplink data splittransmission, an identifier of a MAC entity, information of a primaryRLC entity, information of a secondary RLC entity, and indicationinformation for indicating whether the primary RLC entity and thesecondary RLC entity belong to the same cell group.

Optionally, the configuration information is carried in at least one ofthe following signaling: MAC CE, DCI, and RRC signaling.

Optionally, the processing unit 510 is further configured to, accordingto indication information for the first bearer, determine cell groupscorresponding to the primary RLC entity and the secondary RLC entityamong the at least three RLC entities, or determine a cell groupcorresponding to an RLC entity used for split transmission among the atleast three RLC entities.

Optionally, the indication information is used to indicate an RLC entitycorresponding to split transmission among the at least three RLCentities, or to indicate a secondary RLC entity corresponding to splittransmission among the at least three RLC entities, or to indicatewhether an RLC entity among the at least three RLC entities meets splittransmission.

Optionally, if first signaling carries the indication information, or avalue of the indication information is a first value, the indicationinformation is used to indicate that an RLC entity corresponding to acell group different from a cell group corresponding to the primary RLCentity in at least two cell groups configured for the first bearer is asecondary RLC entity; or, if the indication information is not carriedin first signaling or a value of the indication information is a secondvalue, the indication information is used to indicate that in at leasttwo cell groups configured for the first bearer, an RLC entitycorresponding to a cell group which is the same as a cell groupcorresponding to the primary RLC entity is a secondary RLC entity; or,if first signaling carries the indication information or a value of theindication information is a first value, the indication information isused to indicate that in at least two cell groups configured for thefirst bearer, only an RLC entity corresponding to a cell group differentfrom a cell group corresponding to the primary RLC entity is a secondaryRLC entity; or, if the indication information is not carried in firstsignaling, or a value of the indication information is a second value,the indication information is used to indicate that in at least two cellgroups configured for the first bearer, an RLC entity corresponding to acell group which is the same as or different from a cell groupcorresponding to the primary RLC entity is a secondary RLC entity.

Optionally, if the indication information is not carried in firstsignaling, or a value of the indication information is a first value,the indication information is used to indicate that an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity in at least two cell groups configured for thefirst bearer is a secondary RLC entity; or, if first signaling carriesthe indication information or a value of the indication information is asecond value, the indication information is used to indicate that in atleast two cell groups configured for the first bearer, an RLC entitycorresponding to a cell group which is the same as a cell groupcorresponding to the primary RLC entity is a secondary RLC entity; or,if the indication information is not carried in first signaling, or avalue of the indication information is a first value, the indicationinformation is used to indicate that in at least two cell groupsconfigured for the first bearer, only an RLC entity corresponding to acell group different from a cell group corresponding to the primary RLCentity is a secondary RLC entity; or, if first signaling carries theindication information, or a value of the indication information is asecond value, the indication information is used to indicate that in atleast two cell groups configured for the first bearer, an RLC entitycorresponding to a cell group which is the same as or different from acell group corresponding to the primary RLC entity is a secondary RLCentity.

Optionally, the indication information occupies a resource of 1 bit,wherein the first value is 1 and the second value is 0, or the firstvalue is 0 and the second value is 1.

Optionally, the first signaling is at least one of the followingsignaling: MAC CE, DCI, and RRC signaling.

Optionally, the indication information is configured throughconfiguration information for the first bearer, or configured for aterminal device, or configured for a cell group.

Optionally, in some implementations, the processing unit may be one ormore processors.

It should be understood that the terminal device 500 according to animplementation of the present disclosure may correspond to the terminaldevice in a method implementation of the present disclosure, and theabove-mentioned and other operations and/or functions of various unitsin the terminal device 500 are respectively for implementing thecorresponding flows of the terminal device in the method 200 as shown inFIG. 3 , which will not be repeated here for brevity.

FIG. 15 is a schematic block diagram of a terminal device 600 accordingto an implementation of the present disclosure. As shown in FIG. 15 ,the terminal device 600 includes a processing unit 610.

In a case that duplication transmission of a first bearer isdeactivated, the processing unit 610 is configured to determine cellgroups corresponding to a primary RLC entity and a secondary RLC entityamong at least three RLC entities configured for the first beareraccording to indication information for the first bearer; the processingunit 610 is configured to determine an RLC entity for transmitting aPDCP PDU according to cell groups corresponding to the primary RLCentity and the secondary RLC entity among the at least three RLCentities, and/or the processing unit 610 is configured to determine aMAC entity to which PDCP data volume pending for transmission is mappedaccording to cell groups corresponding to the primary RLC entity and thesecondary RLC entity among the at least three RLC entities.

Optionally, the indication information is used to indicate an RLC entitycorresponding to split transmission among the at least three RLCentities, or to indicate a secondary RLC entity corresponding to splittransmission among the at least three RLC entities, or to indicatewhether an RLC entity among the at least three RLC entities meets splittransmission.

Optionally, if first signaling carries the indication information, or avalue of the indication information is a first value, the indicationinformation is used to indicate that an RLC entity corresponding to acell group different from a cell group corresponding to the primary RLCentity in at least two cell groups configured for the first bearer is asecondary RLC entity; or, if the indication information is not carriedin first signaling, or a value of the indication information is a secondvalue, the indication information is used to indicate that an RLC entitycorresponding to a cell group which is the same as a cell groupcorresponding to the primary RLC entity in at least two cell groupsconfigured for the first bearer is a secondary RLC entity; or, if firstsignaling carries the indication information, or a value of theindication information is a first value, the indication information isused to indicate that only an RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity; or, if the indication information is not carried in firstsignaling, or a value of the indication information is a second value,the indication information is used to indicate that an RLC entitycorresponding to a cell group which is the same as or different from acell group corresponding to the primary RLC entity in at least two cellgroups configured for the first bearer is a secondary RLC entity.

Optionally, if the indication information is not carried in firstsignaling, or a value of the indication information is a first value,the indication information is used to indicate that an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity in at least two cell groups configured for thefirst bearer is a secondary RLC entity; or, if the indicationinformation is carried in first signaling or a value of the indicationinformation is a second value, the indication information is used toindicate that an RLC entity corresponding to a cell group which is thesame as a cell group corresponding to the primary RLC entity in at leasttwo cell groups configured for the first bearer is a secondary RLCentity; or, if the indication information is not carried in firstsignaling, or a value of the indication information is a first value,the indication information is used to indicate that only an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity in at least two cell groups configured for thefirst bearer is a secondary RLC entity; or, if first signaling carriesthe indication information, or a value of the indication information isa second value, the indication information is used to indicate that anRLC entity corresponding to a cell group which is the same as ordifferent from a cell group corresponding to the primary RLC entity inat least two cell groups configured for the first bearer is a secondaryRLC entity.

Optionally, the indication information occupies a resource of 1 bit,wherein the first value is 1 and the second value is 0, or the firstvalue is 0 and the second value is 1.

Optionally, the first signaling is at least one of the followingsignaling: MAC CE, DCI, and RRC signaling.

Optionally, the indication information is configured throughconfiguration information for the first bearer, or configured for theterminal device, or configured for a cell group.

Optionally, the processing unit 610 is configured to determine the RLCentity for transmitting the PDCP PDU according to the cell groupscorresponding to the primary RLC entity and the secondary RLC entityamong the at least three RLC entities, including at least one of thefollowing: if the primary RLC entity and the secondary RLC entitycorrespond to different cell groups, the processing unit 610 isconfigured to determine to use the primary RLC entity and the secondaryRLC entity to transmit a PDCP PDU through split transmission, or totransmit a PDCP PDU to the primary RLC entity and the secondary RLCentity; if the primary RLC entity and the secondary RLC entitycorrespond to the same cell group, the processing unit 610 is configuredto determine to use the primary RLC entity or the secondary RLC entityto transmit a PDCP PDU, or to transmit a PDCP PDU to the primary RLCentity or the secondary RLC entity; if the primary RLC entity and thesecondary RLC entity correspond to the same cell group, the processingunit 610 is configured to determine to use a first RLC entity and asecond RLC entity to transmit a PDCP PDU through split transmission, orto transmit a PDCP PDU to a first RLC entity and a second RLC entity; ifthe primary RLC entity and the secondary RLC entity correspond to thesame cell group and a condition for split transmission is met, theprocessing unit 610 is configured to determine to use a first RLC entityand a second RLC entity to transmit a PDCP PDU through splittransmission, or to transmit a PDCP PDU to a first RLC entity and asecond RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is not met, the processing unit 610 is configured todetermine to use the primary RLC entity or the secondary RLC entity totransmit a PDCP PDU, or to transmit a PDCP PDU to the primary RLC entityor the secondary RLC entity; if a cell group which is the same as a cellgroup corresponding to the primary RLC entity in at least two cellgroups configured for the first bearer only corresponds to one RLCentity and the one RLC entity is the primary RLC entity, the processingunit 610 is configured to determine to use the primary RLC entity totransmit a PDCP PDU, or to transmit a PDCP PDU to the primary RLCentity; if there is only one RLC entity in a MAC entity where theprimary RLC entity is located, the processing unit 610 is configured todetermine that an RLC entity corresponding to a cell group differentfrom a cell group corresponding to the primary RLC entity is thesecondary RLC entity, and the processing unit 610 is configured todetermine to use the primary RLC entity and the secondary RLC entity totransmit a PDCP PDU through split transmission, or to transmit a PDCPPDU to the primary RLC entity and the secondary RLC entity; and if thereare multiple RLC entities in a MAC entity where the primary RLC entityis located, and there is an RLC entity exists in a MAC entity differentfrom the MAC entity where the primary RLC entity is located, theprocessing unit 610 is configured to determine that an RLC entitycorresponding to a cell group different from a cell group correspondingto the primary RLC entity is the secondary RLC entity, and theprocessing unit 610 is configured to determine to use the primary RLCentity and the secondary RLC entity to transmit a PDCP PDU through splittransmission, or the processing unit 610 is configured to transmit aPDCP PDU to the primary RLC entity and the secondary RLC entity.

Optionally, the processing unit 610 is configured to determine the MACentity to which the PDCP data volume pending for transmission is mappedaccording to the cell groups corresponding to the primary RLC entity andthe secondary RLC entity among the at least three RLC entities,including at least one of the following: if the primary RLC entity andthe secondary RLC entity correspond to different cell groups, theprocessing unit 610 is configured to map the PDCP data volume pendingfor transmission to a MAC entity corresponding to the primary RLC entityand a MAC entity corresponding to the secondary RLC entity; if theprimary RLC entity and the secondary RLC entity correspond to the samecell group, the processing unit 610 is configured to map the PDCP datavolume pending for transmission to a MAC entity corresponding to theprimary RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group, the processing unit 610 mapsthe PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity and a MAC entity correspondingto the secondary RLC entity; if the primary RLC entity and the secondaryRLC entity correspond to the same cell group and a condition for splittransmission is met, the processing unit 610 maps the PDCP data volumepending for transmission to a MAC entity corresponding to the primaryRLC entity and a MAC entity corresponding to the secondary RLC entity;if the primary RLC entity and the secondary RLC entity correspond to thesame cell group, the processing unit 610 is configured to map the PDCPdata volume pending for transmission to a MAC entity corresponding tothe primary RLC entity and map 0 to a MAC entity corresponding to thesecondary RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group, the processing unit 610 isconfigured to map the PDCP data volume pending for transmission to a MACentity corresponding to a first RLC entity and a MAC entitycorresponding to a second RLC entity; if the primary RLC entity and thesecondary RLC entity correspond to the same cell group and a conditionfor split transmission is met, the processing unit 610 is configured tomap the PDCP data volume pending for transmission to a MAC entitycorresponding to a first RLC entity and a MAC entity corresponding to asecond RLC entity; if the primary RLC entity and the secondary RLCentity correspond to the same cell group and a condition for splittransmission is not met, the processing unit 610 is configured to mapthe PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity; if the primary RLC entity andthe secondary RLC entity correspond to the same cell group and acondition for split transmission is not met, the processing unit 610 isconfigured to map the PDCP data volume pending for transmission to a MACentity corresponding to the primary RLC entity and map 0 to a MAC entitycorresponding to the secondary RLC entity; if a cell group which is thesame as a cell group corresponding to the primary RLC entity in at leasttwo cell groups configured for the first bearer only corresponds to oneRLC entity and the one RLC entity is the primary RLC entity, theprocessing unit 610 is configured to determine to use the primary RLCentity to transmit a PDCP PDU, or the processing unit 610 is configuredto map the PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity; if there is only one RLC entityin a MAC entity where the primary RLC entity is located, the processingunit 610 is configured to determine that an RLC entity corresponding toa cell group different from a cell group corresponding to the primaryRLC entity is the secondary RLC entity, and the processing unit 610 isconfigured to map the PDCP data volume pending for transmission to a MACentity corresponding to the primary RLC entity and a MAC entitycorresponding to the secondary RLC entity; and if there are multiple RLCentities in a MAC entity where the primary RLC entity is located, andthere is an RLC entity in a MAC entity different from the MAC entitywhere the primary RLC entity is located, the processing unit 610 isconfigured to determine an RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the primary RLC entity asthe secondary RLC entity, and the processing unit 610 is configured tomap the PDCP data volume pending for transmission to a MAC entitycorresponding to the primary RLC entity and a MAC entity correspondingto the secondary RLC entity.

Optionally, the first RLC entity and the second RLC entity correspond todifferent cell groups.

Optionally, the first RLC entity is the primary RLC entity, and thesecond RLC entity is a specific RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the first RLC entity; or,the first RLC entity is the secondary RLC entity, and the second RLCentity is a specific RLC entity corresponding to a cell group differentfrom a cell group corresponding to the first RLC entity; or, the firstRLC entity is the secondary RLC entity and the second RLC entity is theprimary RLC entity; or, the first RLC entity is the primary RLC entity,and the second RLC entity is the secondary RLC entity.

Optionally, the specific RLC entity is one of the following: any one RLCentity, an RLC entity with the smallest index identifier, an RLC entitywith the largest index identifier, an RLC entity with the best channelquality, and an indicated RLC entity.

Optionally, the condition for split transmission includes that datavolume pending for transmission corresponding to the first bearer isgreater than or equal to a threshold.

Optionally, the data volume pending for transmission corresponding tothe first bearer is one of the following: in all RLC entities configuredfor the first bearer, a total amount of PDCP data volume and RLC datavolume pending for initial transmission; in an activated RLC entityconfigured for the first bearer, a total amount of PDCP data volume andRLC data volume pending for initial transmission; in an RLC entity thathad been activated and is configured for the first bearer, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer and has data pending for initial transmission, atotal amount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer for initial transmission of data, a total amount ofPDCP data volume and RLC data volume pending for initial transmission; atotal amount of PDCP data volume and RLC data volume pending for initialtransmission in the primary RLC entity and the secondary RLC entity; anda total amount of PDCP data volume and RLC data volume pending fortransmission in the primary RLC entity and the secondary RLC entity.

Optionally, the processing unit 610 is further configured to determinecell groups corresponding to the primary RLC entity and the secondaryRLC entity among the at least three RLC entities according toconfiguration information for the first bearer.

Optionally, the configuration information includes at least one of thefollowing: an identifier of the first bearer, an identifier of an RLCentity, an LCH identifier, an identifier of a cell group, the number ofRLC entities, a threshold of uplink data split transmission, anidentifier of a MAC entity, information of a primary RLC entity,information of a secondary RLC entity, and indication information forindicating whether the primary RLC entity and the secondary RLC entitybelong to the same cell group.

Optionally, the configuration information is carried in at least one ofthe following signaling: MAC CE, DCI, and RRC signaling.

Optionally, in some implementations, the processing unit may be one ormore processors.

It should be understood that the terminal device 600 according to animplementation of the present disclosure may correspond to the terminaldevice in a method implementation of the present disclosure, and theabove-mentioned and other operations and/or functions of various unitsin the terminal device 600 are respectively for implementing thecorresponding flows of the terminal device in the method 300 as shown inFIG. 12 , which will not be repeated here for brevity.

FIG. 16 is a schematic block diagram of a terminal device 700 accordingto an implementation of the present disclosure. As shown in FIG. 16 ,the terminal device 700 includes a processing unit 710.

In a case that duplication transmission of a first bearer is deactivatedand there is no secondary RLC entity or no secondary RLC entity isconfigured among at least three RLC entities configured for the firstbearer, the processing unit 710 is configured to determine whether tocarry out split transmission, or determine an RLC entity fortransmitting a PDCP PDU.

Optionally, the processing unit 710 is configured to determine the RLCentity for transmitting a PDCP PDU, including one of the following: theprocessing unit 710 is configured to determine to use a primary RLCentity among the at least three RLC entities to transmit a PDCP PDU, orthe processing unit 710 is configured to transmit a PDCP PDU to aprimary RLC entity among the at least three RLC entities; if a conditionfor split transmission is met, the processing unit 710 is configured todetermine to use a first RLC entity and a second RLC entity among the atleast three RLC entities to transmit a PDCP PDU through splittransmission, or to transmit a PDCP PDU to a first RLC entity and asecond RLC entity among the at least three RLC entities; and if acondition for split transmission is not met, the processing unit 710 isconfigured to determine to use a primary RLC entity among the at leastthree RLC entities to transmit a PDCP PDU, or the processing unit 710 isconfigured to transmit a PDCP PDU to a primary RLC entity among the atleast three RLC entities.

Optionally, the first RLC entity and the second RLC entity correspond todifferent cell groups.

Optionally, the first RLC entity is the primary RLC entity, and thesecond RLC entity is a specific RLC entity corresponding to a cell groupdifferent from a cell group corresponding to the first RLC entity.

Optionally, the specific RLC entity is one of the following: any one RLCentity, an RLC entity with the smallest index identifier, an RLC entitywith the largest index identifier, an RLC entity with the best channelquality, and an indicated RLC entity.

Optionally, the condition for split transmission includes that datavolume pending for transmission corresponding to the first bearer isgreater than or equal to a threshold.

Optionally, the data volume pending for transmission corresponding tothe first bearer is one of the following: in all RLC entities configuredfor the first bearer, a total amount of PDCP data volume and RLC datavolume pending for initial transmission; in an activated RLC entityconfigured for the first bearer, a total amount of PDCP data volume andRLC data volume pending for initial transmission; in an RLC entity thathad been activated and is configured for the first bearer, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; in an RLC entity that had been activated and is configuredfor the first bearer and has data pending for transmission, a totalamount of PDCP data volume and RLC data volume pending for initialtransmission; and in an RLC entity that had been activated and isconfigured for the first bearer for initial transmission of data, atotal amount of PDCP data volume and RLC data volume pending for initialtransmission.

Optionally, the processing unit 710 is further configured to determinethat there is no secondary RLC entity among the at least three RLCentities according to configuration information for the first bearer.

Optionally, the configuration information includes at least one of thefollowing: an identifier of the first bearer, an identifier of an RLCentity, a Logical Channel (LCH) identifier, an identifier of a cellgroup, the number of RLC entities, a threshold of uplink data splittransmission, an identifier of a MAC entity, and information of aprimary RLC entity.

Optionally, the configuration information is carried in at least one ofthe following signaling: MAC CE, DCI, and RRC signaling.

Optionally, in some implementations, the processing unit may be one ormore processors.

It should be understood that the terminal device 700 according to animplementation of the present disclosure may correspond to the terminaldevice in a method implementation of the present disclosure, and theabove-mentioned and other operations and/or functions of various unitsin the terminal device 700 are respectively for implementing thecorresponding flows of the terminal device in the method 400 as shown inFIG. 13 , which will not be repeated here for brevity.

FIG. 17 is a schematic structural diagram of a communication device 800provided according to an implementation of the present disclosure. Thecommunication device 800 shown in FIG. 17 includes a processor 810 thatmay call and run a computer program from a memory to implement themethods in the implementations of the present disclosure.

Optionally, as shown in FIG. 17 , the communication device 800 mayfurther include a memory 820. The processor 810 may call and run thecomputer program from the memory 820 to implement the methods in theimplementations of the present disclosure.

The memory 820 may be a separate device independent of the processor 810or may be integrated in the processor 810.

Optionally, as shown in FIG. 17 , the communication device 800 mayfurther include a transceiver 830, and the processor 810 may control thetransceiver 830 to communicate with other devices. Specifically, thetransceiver 830 may send information or data to other devices or receiveinformation or data sent by other devices.

The transceiver 830 may include a transmitter and a receiver. Thetransceiver 830 may further include antennas, and the number of whichmay be one or more.

Optionally, the communication device 800 may specifically be a networkdevice or a base station of the implementations of the presentdisclosure, and the communication device 800 may implement thecorresponding processes implemented by a network device or a basestation in various methods of the implementations of the presentdisclosure, which will not be repeated herein for brevity.

Optionally, the communication device 800 may be specifically the mobileterminal/terminal device in accordance with an implementation of thepresent disclosure, and the communication device 800 may implement thecorresponding processes implemented by the mobile terminal/terminaldevice in various methods in the implementations of the presentdisclosure, which will not be described repeatedly herein for brevity.

FIG. 18 is a schematic diagram of a structure of an apparatus inaccordance with an implementation of the present disclosure. Theapparatus 900 shown in FIG. 18 includes a processor 910. The processor910 may call and run a computer program from a memory to implement themethods in the implementations of the present disclosure.

Optionally, as shown in FIG. 18 , the apparatus 900 may further includea memory 920. The processor 910 may call and run a computer program fromthe memory 920 to implement the methods in the implementations of thepresent disclosure.

The memory 920 may be a separate device independent of the processor 910or may be integrated in the processor 910.

Optionally, the apparatus 900 may further include an input interface930. The processor 910 may control the input interface 930 tocommunicate with other devices or chips. Specifically, the processor 910may acquire information or data sent by other devices or chips.

Optionally, the apparatus 900 may further include an output interface940. The processor 910 may control the output interface 940 tocommunicate with other devices or chips. Specifically, the processor 910may output information or data to other devices or chips.

Optionally, the apparatus may be applied to a network device or a basestation in the implementations of the present disclosure, and theapparatus may implement the corresponding processes implemented by anetwork device or a base station in various methods in theimplementations of the present disclosure, which will not be repeatedherein for brevity.

Optionally, the apparatus may be applied to a mobile terminal/terminaldevice in the implementations of the present disclosure, and theapparatus may implement the corresponding processes implemented by amobile terminal/terminal device in various methods in theimplementations of the present disclosure, which will not be describedrepeatedly herein for brevity.

Optionally, the apparatus mentioned in the implementations of thepresent disclosure may be a chip. For example, it may be a system-levelchip, a system chip, a system-on-chip, or a system chip on chip.

FIG. 19 is a schematic block diagram of a communication system 1000provided according to an implementation of the present disclosure. Asshown in FIG. 19 , the communication system 1000 may include a terminaldevice 1010 and a network device 1020.

The terminal device 1010 may be configured to implement thecorresponding functions implemented by a terminal device in theabove-mentioned methods, and the network device 1020 may be configuredto implement the corresponding functions implemented by a network deviceor a base station in the above-mentioned methods, which will not berepeated here for brevity.

It should be understood that the processor in the implementations of thepresent disclosure may be an integrated circuit chip having a signalprocessing capability. In an implementation process, each of the acts ofthe foregoing method implementations may be completed through anintegrated logic circuit of hardware in the processor or instructions ina form of software. The processor described above may be a generalpurpose processor, a Digital Signal Processor (DSP), an ApplicationSpecific Integrated Circuit (ASIC), a Field Programmable Gate Array(FPGA) or other programmable logic devices, a discrete gate or atransistor logic device, or a discrete hardware component. The processormay implement or perform various methods, acts and logical blockdiagrams disclosed in the implementations of the present disclosure. Thegeneral purpose processor may be a microprocessor, or the processor mayalso be any conventional processor, or the like. The acts of the methodsdisclosed in the implementations of the present disclosure may bedirectly implemented by a hardware decoding processor, or may beimplemented by a combination of hardware and software modules in thedecoding processor. The software modules may be located in a storagemedium which is mature in the art, such as a random access memory, aflash memory, a read-only memory, a programmable read-only memory, anelectrically erasable programmable memory, a register, etc. The storagemedium is located in the memory, and the processor reads information inthe memory and completes the acts of the foregoing methods incombination with its hardware.

It may be understood that the memory in the implementations of thepresent disclosure may be a volatile memory or a non-volatile memory, ormay include both a volatile memory and a non-volatile memory. Thenon-volatile memory may be a read-only Memory (ROM), a programmableread-only memory (PROM), an erasable programmable read-only memory(EPROM), an electrically erasable programmable read-only memory(EEPROM), or a flash memory. The volatile memory may be a random accessmemory (RAM), which is used as an external cache. Through exemplary butnon-restrictive description, many forms of RAMs may be available, suchas a static random access memory (SRAM), a dynamic random access memory(DRAM), a synchronous dynamic random access memory (SDRAM), a doubledata rate synchronous dynamic random access memory (DDR SDRAM), anenhanced synchronous dynamic random access memory (ESDRAM), asynchronous link dynamic random access memory (SLDRAM), and a directRambus dynamic random access memory (DR RAM). It should be noted thatthe memories in the systems and methods described herein are intended toinclude, but are not limited to, these and any other suitable types ofmemories.

It should be understood that the foregoing memory is described in anexemplary but non-limiting sense. For example, the memory in theimplementations of the present disclosure may also be a Static RAM(SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double DataRate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM(SLDRAM), a direct Rambus RAM (DR RAM), or the like. That is, thememories in the implementations of the present disclosure are intendedto include, but are not limited to, these and any other suitable type ofmemories.

An implementation of the present disclosure further provides acomputer-readable storage medium configured to store a computer program.

Optionally, the computer readable storage medium may be applied to anetwork device or a base station in the implementations of the presentdisclosure, and the computer program enables a computer to perform thecorresponding processes implemented by a network device or a basestation in various methods of the implementations of the presentdisclosure, which will not be repeated here for brevity.

Optionally, the computer readable storage medium may be applied to amobile terminal/terminal device in the implementations of the presentdisclosure, and the computer program enables a computer to perform thecorresponding processes implemented by a mobile terminal/terminal devicein various methods in accordance with the implementations of the presentdisclosure, which will not be described repeatedly for brevity.

An implementation of the present disclosure further provides a computerprogram product including computer program instructions.

Optionally, the computer program product may be applied to a networkdevice or a base station in the implementations of the presentdisclosure, and the computer program instructions enable a computer toperform the corresponding processes implemented by a network device or abase station in various methods of the implementations of the presentdisclosure, which will not be repeated here for brevity.

Optionally, the computer program product may be applied to a mobileterminal/terminal device in implementations of the present disclosure,and the computer program instructions enable a computer to perform thecorresponding processes implemented by a mobile terminal/terminal devicein various methods of the implementations of the present disclosure,which will not be repeated here for brevity.

An implementation of the present disclosure further provides a computerprogram.

Optionally, the computer program may be applied to a network device or abase station in the implementations of the present disclosure. When thecomputer program is run on a computer, the computer is enabled toperform the corresponding processes implemented by a network device or abase station in various methods of the implementations of the presentdisclosure, which will not be repeated here for brevity.

Optionally, the computer program may be applied to a mobileterminal/terminal device in implementations of the present disclosure.When the computer program is run on a computer, the computer is enabledto perform the corresponding processes implemented by a mobileterminal/terminal device in various methods of the implementations ofthe present disclosure, which will not be repeated here for brevity.

Those of ordinary skill in the art will recognize that the exemplaryelements and algorithm acts in combination with the implementationsdisclosed herein may be implemented in electronic hardware, or acombination of computer software and electronic hardware. Whether thesefunctions are implemented in hardware or software depends on thespecific application and design constraints of the technical solution.Those skilled in the art may use different methods to implement thedescribed functions for each particular application, but suchimplementation should not be considered to be beyond the scope of thepresent disclosure.

Those skilled in the art may clearly understand that for the sake ofconvenience and conciseness of description, the specific workingprocesses of the systems, devices and units described above may bedescribed with reference to the corresponding processes in the abovemethod implementations and will not be repeated herein.

In several implementations provided by the present disclosure, it shouldbe understood that the disclosed systems, devices and methods may beimplemented in another manner. For example, the device implementationsdescribed above are only illustrative, for example, the division of theunits is only a logical function division, and there may be otherdivision manners in actual implementation. For example, multiple unitsor components may be combined or integrated into another system, or somefeatures may be ignored or not executed. On the other hand, the mutualcoupling or direct coupling or communication connection shown ordiscussed may be indirect coupling or communication connection betweenapparatuses or units through some interfaces, or may be in electrical,mechanical or other forms.

The unit described as a separate component may or may not be physicallyseparated, and the component shown as a unit may or may not be aphysical unit, i.e., it may be located in one place or may bedistributed across multiple network units. Part or all of the units maybe selected according to actual needs to achieve the purpose of theimplementations.

In addition, various functional units in various implementations of thepresent disclosure may be integrated into one processing unit, or mayexist physically separately, or two or more than two units may beintegrated into one unit.

The function, if achieved in a form of software functional units andsold or used as a separate product, may be stored in a computer-readablestorage medium. Regarding such understanding, the technical solution ofthe present disclosure, in essence, or the part contributing to theprior art, or the part of the technical solution, may be embodied in aform of a software product, wherein the computer software product isstored in a storage medium, and includes a number of instructions forcausing a computer device (which may be a personal computer, a server,or a network device, or the like) to perform all or part of the acts ofthe methods described in various implementations of the presentdisclosure. The aforementioned storage medium includes: any medium thatare capable of storing program codes, such as a USB flash drive, aremovable hard disk, a Read-Only Memory (ROM), a Random Access Memory(RAM), a magnetic disk, or an optical disk.

What are described above are merely specific implementations of thepresent disclosure, but the protection scope of the present disclosureis not limited thereto. Any variation or substitution that may be easilyconceived by a person skilled in the art within the technical scopedisclosed by the present disclosure shall be included within theprotection scope of the present disclosure. Therefore, the protectionscope of the present disclosure shall be subject to the protection scopeof the claims.

What is claimed is:
 1. A wireless communication method, comprising:receiving, by a terminal device, indication information of a networkdevice for a first bearer, wherein the indication information indicatesa secondary Radio Link Control (RLC) entity, which corresponds to a cellgroup different from a cell group corresponding to a primary RLC entityin at least two cell groups configured for the first bearer;determining, by the terminal device, cell groups corresponding to theprimary RLC entity and the secondary RLC entity among at least three RLCentities according to the indication information; in a case thatduplication transmission of the first bearer is deactivated,determining, by the terminal device, to use the primary RLC entity orthe secondary RLC entity to transmit a Packet Data Convergence Protocol(PDCP) Protocol Data Units (PDU) through split transmission according tothe cell groups.
 2. A terminal device, comprising a processor and atransceiver, wherein the processor is configured to: receive indicationinformation of a network device for a first bearer, wherein theindication information indicates a secondary Radio Link Control (RLC)entity, which corresponds to a cell group different from a cell groupcorresponding to a primary RLC entity in at least two cell groupsconfigured for the first bearer; determine cell groups corresponding tothe primary RLC entity and the secondary RLC entity among at least threeRLC entities according to the indication information; and in a case thatduplication transmission of the first bearer is deactivated, determineto use the primary RLC entity or the secondary RLC entity to transmit aPacket Data Convergence Protocol (PDCP) Protocol Data Units (PDU)through split transmission according to the cell groups.